From ba7b4070235c67bef52a0a3d218f9678d498c0fb Mon Sep 17 00:00:00 2001 From: "Karl O. Pinc kop@karlpinc.com" Date: Thu, 23 Jul 2026 23:32:25 +0000 Subject: [PATCH] Spelling --- doc/src/views/obs.m4 | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/src/views/obs.m4 b/doc/src/views/obs.m4 index 390abdd..660c5f8 100644 --- a/doc/src/views/obs.m4 +++ b/doc/src/views/obs.m4 @@ -34,8 +34,8 @@ OBS (OBservationS) OBS rows are |EVENTS| rows, but extended with the date, |BIOGRAPHY_DATA.AnimID|, and other information found on |WATCHES|. -The OBS view is convienent when writing queries, instead of having to -``JOIN`` |EVENTS| with |WATCHES| every time behavior is queryed. +The OBS view is convenient when writing queries, instead of having to +``JOIN`` |EVENTS| with |WATCHES| every time behavior is queried. For example, below is a query that returns all the arrivals and departures from the feeding station attendance records, showing @@ -154,7 +154,7 @@ Columns of the OBS View +-----------------+-------------------------------------------------+---------------------------------------------------------------------+ | Date | |WATCHES|.\ |WATCHES.Date| | Date of the event | +-----------------+-------------------------------------------------+---------------------------------------------------------------------+ - | AnimID | |WATCHES|.\ |WATCHES.AnimID| | Focal of follow, or focal of a non-existant follow, or an | + | AnimID | |WATCHES|.\ |WATCHES.AnimID| | Focal of follow, or focal of a non-existent follow, or an | | | | un-interesting AnimID | +-----------------+-------------------------------------------------+---------------------------------------------------------------------+ | Type | |WATCHES|.\ |WATCHES.Type| | Category of observation, often determining the data collection | @@ -218,8 +218,8 @@ DELETE .. rubric:: Footnotes .. [#f4] - In the case of groomings, because they are dyadic interctions, it - can be more convienient to use the |DYADS| view. + In the case of groomings, because they are dyadic interactions, it + can be more convenient to use the |DYADS| view. When using |DYADS| it is no longer necessary to test for the role played by the individual performing the grooming because the view places the individual who groomed in the Actor column. @@ -255,7 +255,7 @@ DELETE also recorded in a related |ROLES| row, in the |ROLES|.\ |ROLES.Participant| column. - The |ROLES|.\ |ROLES.Participant| column is the recommened column + The |ROLES|.\ |ROLES.Participant| column is the recommended column to obtain event participant information from, only because you don't need to be aware of all the rules regarding what might be in the OBS.\ |WATCHES.AnimID| column. @@ -266,6 +266,6 @@ DELETE The point is, care must be taken when querying to ensure that the query actually retrieves the information that it is expected to. - Familarity with the database structure, the data itself, the + Familiarity with the database structure, the data itself, the procedures used to collect and record the data, and how all of this changed over time is critical for accurate results. -- 2.34.1